Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 453c7b00e345ee7be24b24de2960687236a20bbfaefd7209de6c40913bd94bf5

Tx prefix hash: 2f70f36e38196302b04b944a7a20d5efde7baa4fe29b15dbcd1cc955d482f5be
Tx public key: 495132f4327408191a0fae8dd28a656dd4190acc85a30b38e9f65802f5c6c097
Timestamp: 1639389911 Timestamp [UCT]: 2021-12-13 10:05:11 Age [y:d:h:m:s]: 02:351:04:37:58
Block: 394544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769081 RingCT/type: yes/0
Extra: 01495132f4327408191a0fae8dd28a656dd4190acc85a30b38e9f65802f5c6c097021100000011eaa12622000000000000000000

1 output(s) for total of 30.249089328000 dcy

stealth address amount amount idx
00: 232a95fc44bc49a1073766e0b9ace07ef3a1d5ebd9568c254b9d34ccb0c91b8e 30.249089328000 792171 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": 394554, "vin": [ { "gen": { "height": 394544 } } ], "vout": [ { "amount": 30249089328, "target": { "key": "232a95fc44bc49a1073766e0b9ace07ef3a1d5ebd9568c254b9d34ccb0c91b8e" } } ], "extra": [ 1, 73, 81, 50, 244, 50, 116, 8, 25, 26, 15, 174, 141, 210, 138, 101, 109, 212, 25, 10, 204, 133, 163, 11, 56, 233, 246, 88, 2, 245, 198, 192, 151, 2, 17, 0, 0, 0, 17, 234, 161, 38, 34, 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