Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b188a7abda31df8e58863d56c43d130c7927d250a7ad71e834cb10dd41d4ccf

Tx prefix hash: 7721c91dc8b51dc24e10515c9747d170c411c3154e6833bd88bebf9877ebd569
Tx public key: 9a20cd8a2c3cc7dccf11c427581fe8c1767c11bec4158567289cd73091236de6
Timestamp: 1583633905 Timestamp [UCT]: 2020-03-08 02:18:25 Age [y:d:h:m:s]: 04:353:11:37:10
Block: 78353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147184 RingCT/type: yes/0
Extra: 019a20cd8a2c3cc7dccf11c427581fe8c1767c11bec4158567289cd73091236de602110000000181a90efe000000000000000000

1 output(s) for total of 337.586271864000 dcy

stealth address amount amount idx
00: d465164efa4670699d1b85a2c49a3b206517f7c98e6fd4b6817fbfa482b905d6 337.586271864000 143797 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": 78363, "vin": [ { "gen": { "height": 78353 } } ], "vout": [ { "amount": 337586271864, "target": { "key": "d465164efa4670699d1b85a2c49a3b206517f7c98e6fd4b6817fbfa482b905d6" } } ], "extra": [ 1, 154, 32, 205, 138, 44, 60, 199, 220, 207, 17, 196, 39, 88, 31, 232, 193, 118, 124, 17, 190, 196, 21, 133, 103, 40, 156, 215, 48, 145, 35, 109, 230, 2, 17, 0, 0, 0, 1, 129, 169, 14, 254, 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