Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: beed6c1049570fe40dcd2a7c7445d98221da15ba743066a7c3bc28efc28bc991

Tx prefix hash: 258b2f5699452627546fc47f087710b4491fd2bfdbd9ac2102a901b82c44e5e6
Tx public key: f4750daf6fda392a28c057f0985f38eb46bb187314b62b4a817d3302b82ae387
Timestamp: 1676929097 Timestamp [UCT]: 2023-02-20 21:38:17 Age [y:d:h:m:s]: 02:053:22:19:25
Block: 701351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560155 RingCT/type: yes/0
Extra: 01f4750daf6fda392a28c057f0985f38eb46bb187314b62b4a817d3302b82ae38702110000000375e3f0e9000000000000000000

1 output(s) for total of 2.911607998000 dcy

stealth address amount amount idx
00: 8f511fb17be3b056713375e84d2bf0c206f0ca5c3dc1b5bd58acaf5663d0e618 2.911607998000 1144830 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 701361, "vin": [ { "gen": { "height": 701351 } } ], "vout": [ { "amount": 2911607998, "target": { "key": "8f511fb17be3b056713375e84d2bf0c206f0ca5c3dc1b5bd58acaf5663d0e618" } } ], "extra": [ 1, 244, 117, 13, 175, 111, 218, 57, 42, 40, 192, 87, 240, 152, 95, 56, 235, 70, 187, 24, 115, 20, 182, 43, 74, 129, 125, 51, 2, 184, 42, 227, 135, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8