Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 682107252fd8c420f1cd411be2309e69269f3f3f22a66b6b9afa6a467644e5ab

Tx prefix hash: 18ac7c65d83a330cdb2e9532fc71a84d9bfa50aa73c1694a83f22f0cf48f85a1
Tx public key: 96ab5831d3d3a3e03a02b5ae692ce655b303fdf3810bd50ec221f8ec48dac695
Timestamp: 1587536024 Timestamp [UCT]: 2020-04-22 06:13:44 Age [y:d:h:m:s]: 04:219:16:22:23
Block: 94898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067521 RingCT/type: yes/0
Extra: 0196ab5831d3d3a3e03a02b5ae692ce655b303fdf3810bd50ec221f8ec48dac695021100000015d81c26c0000000000000000000

1 output(s) for total of 297.571217421000 dcy

stealth address amount amount idx
00: 5f35a4319b429de89a71d3d4c4f5a33e2c6f5e57bc733104564c12baf344b097 297.571217421000 168770 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": 94908, "vin": [ { "gen": { "height": 94898 } } ], "vout": [ { "amount": 297571217421, "target": { "key": "5f35a4319b429de89a71d3d4c4f5a33e2c6f5e57bc733104564c12baf344b097" } } ], "extra": [ 1, 150, 171, 88, 49, 211, 211, 163, 224, 58, 2, 181, 174, 105, 44, 230, 85, 179, 3, 253, 243, 129, 11, 213, 14, 194, 33, 248, 236, 72, 218, 198, 149, 2, 17, 0, 0, 0, 21, 216, 28, 38, 192, 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