Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333c1c09ad2f21dc15fefd730448fbf77354b08fb3eeb2110c9f0d43d7bfaa99

Tx prefix hash: 5ff5a866a631e7eb6393a75ddfbc4d78d0a4131a559947db1cd1ca707cb72b70
Tx public key: e55871e68fc44d09afc046e2486d42d760594266839f85c34f01051a031d02ee
Timestamp: 1635957084 Timestamp [UCT]: 2021-11-03 16:31:24 Age [y:d:h:m:s]: 03:131:23:05:53
Block: 366586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872628 RingCT/type: yes/0
Extra: 01e55871e68fc44d09afc046e2486d42d760594266839f85c34f01051a031d02ee021100000001f56b629f000000000000000000

1 output(s) for total of 37.441117639000 dcy

stealth address amount amount idx
00: 18f9c93bfcfcf48c21b2f03fa5dceab89709f739ac07b24c22c21f5b582914a5 37.441117639000 744096 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": 366596, "vin": [ { "gen": { "height": 366586 } } ], "vout": [ { "amount": 37441117639, "target": { "key": "18f9c93bfcfcf48c21b2f03fa5dceab89709f739ac07b24c22c21f5b582914a5" } } ], "extra": [ 1, 229, 88, 113, 230, 143, 196, 77, 9, 175, 192, 70, 226, 72, 109, 66, 215, 96, 89, 66, 102, 131, 159, 133, 195, 79, 1, 5, 26, 3, 29, 2, 238, 2, 17, 0, 0, 0, 1, 245, 107, 98, 159, 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