Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536fe9f24792722b6a3a06ac4074c645df0824f68b06e6ab7b6503511351d982

Tx prefix hash: 17d2b168136fef0e47395c2d71c3c8077b352c5b311d07c0ee5c2170983ef7e8
Tx public key: 9a68e9c6a9e8711c0a56cf74e01c40bea891fa27ac52bce0db37179308258cf5
Timestamp: 1736057448 Timestamp [UCT]: 2025-01-05 06:10:48 Age [y:d:h:m:s]: 00:164:18:24:40
Block: 1190555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117453 RingCT/type: yes/0
Extra: 019a68e9c6a9e8711c0a56cf74e01c40bea891fa27ac52bce0db37179308258cf50211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 524b473fc2bed84b7ba59d625bc95ce5d97b50ded99cc00f424cd6869f6fda6b 0.600000000000 1677072 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": 1190565, "vin": [ { "gen": { "height": 1190555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "524b473fc2bed84b7ba59d625bc95ce5d97b50ded99cc00f424cd6869f6fda6b" } } ], "extra": [ 1, 154, 104, 233, 198, 169, 232, 113, 28, 10, 86, 207, 116, 224, 28, 64, 190, 168, 145, 250, 39, 172, 82, 188, 224, 219, 55, 23, 147, 8, 37, 140, 245, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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