Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b887a6c7ac498da5055c58d402e050a83ff6237bb30e3ee805b62be101c78a94

Tx prefix hash: af52062dac91d34dd22922e6da41465609710e3ee718b8441839e821316e8e34
Tx public key: 17cb4984fec05165b4ad66d4c612edd91f791e29bcd7b4f096e381847ee8e3e8
Timestamp: 1584527867 Timestamp [UCT]: 2020-03-18 10:37:47 Age [y:d:h:m:s]: 04:286:06:13:08
Block: 84930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100207 RingCT/type: yes/0
Extra: 0117cb4984fec05165b4ad66d4c612edd91f791e29bcd7b4f096e381847ee8e3e8021100000004c2c2f844000000000000000000

1 output(s) for total of 321.064609550000 dcy

stealth address amount amount idx
00: 4168132162d7acc3ac89df01c4e23dd19083c0748e7e01f06e0eeb48866804f4 321.064609550000 153722 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": 84940, "vin": [ { "gen": { "height": 84930 } } ], "vout": [ { "amount": 321064609550, "target": { "key": "4168132162d7acc3ac89df01c4e23dd19083c0748e7e01f06e0eeb48866804f4" } } ], "extra": [ 1, 23, 203, 73, 132, 254, 192, 81, 101, 180, 173, 102, 212, 198, 18, 237, 217, 31, 121, 30, 41, 188, 215, 180, 240, 150, 227, 129, 132, 126, 232, 227, 232, 2, 17, 0, 0, 0, 4, 194, 194, 248, 68, 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