Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b582be58d14f8a8afffa0abafeb46fb276908a8e9fcf00b2102e8b785f8fafc3

Tx prefix hash: 4d1f136ebf691078207172190acf6fec37b03e02e7a9b873714f1024be5d4705
Tx public key: b6aa7c8cbb200d81fd56ee54ed9b5940d3e317319d2e8cefc4ddc75c32980473
Timestamp: 1582335198 Timestamp [UCT]: 2020-02-22 01:33:18 Age [y:d:h:m:s]: 05:110:06:44:44
Block: 69840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232098 RingCT/type: yes/0
Extra: 01b6aa7c8cbb200d81fd56ee54ed9b5940d3e317319d2e8cefc4ddc75c329804730211000000020aca7173000000000000000000

1 output(s) for total of 360.246185158000 dcy

stealth address amount amount idx
00: cc4a820eaefb3f883f68da32858f6a5027bdb14e3ee7c3a6da94d89f10f9cb35 360.246185158000 128896 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": 69850, "vin": [ { "gen": { "height": 69840 } } ], "vout": [ { "amount": 360246185158, "target": { "key": "cc4a820eaefb3f883f68da32858f6a5027bdb14e3ee7c3a6da94d89f10f9cb35" } } ], "extra": [ 1, 182, 170, 124, 140, 187, 32, 13, 129, 253, 86, 238, 84, 237, 155, 89, 64, 211, 227, 23, 49, 157, 46, 140, 239, 196, 221, 199, 92, 50, 152, 4, 115, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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