Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13a4c01ef0a3963305a36e3ebf68e3885f0b6d7be0c1f5e264e18891f7d02c3c

Tx prefix hash: 5dd49e0651305fbdc4eb6455a9c6cfb79e926f2caa762757768fb7e7293c79fd
Tx public key: a9c0d668c483ed09d406903b23e08f7610359a582ced87a3a4bc875bd656d805
Timestamp: 1714209628 Timestamp [UCT]: 2024-04-27 09:20:28 Age [y:d:h:m:s]: 00:201:17:02:40
Block: 1009543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144388 RingCT/type: yes/0
Extra: 01a9c0d668c483ed09d406903b23e08f7610359a582ced87a3a4bc875bd656d80502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 601ac24996c8980e3a235d61983dd4de7a40f4b71026a7e8d43cae7513c1eadd 0.600000000000 1471247 of 15

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": 1009553, "vin": [ { "gen": { "height": 1009543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "601ac24996c8980e3a235d61983dd4de7a40f4b71026a7e8d43cae7513c1eadd" } } ], "extra": [ 1, 169, 192, 214, 104, 196, 131, 237, 9, 212, 6, 144, 59, 35, 224, 143, 118, 16, 53, 154, 88, 44, 237, 135, 163, 164, 188, 135, 91, 214, 86, 216, 5, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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