Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 062cd63dfa3fc4b237a72cc8e3ffebd41c0b719fc265154bdc7832f1764a7b3a

Tx prefix hash: 29134f4d209ea6cc0a11bd6bf20a07907004ccea068e6491eca00702741d957a
Tx public key: a89e1947b724c9dd7e41052dd0400a1bdf5416d62b22cbd5e6e079c11a8cb984
Timestamp: 1736773975 Timestamp [UCT]: 2025-01-13 13:12:55 Age [y:d:h:m:s]: 00:064:21:37:55
Block: 1196480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46175 RingCT/type: yes/0
Extra: 01a89e1947b724c9dd7e41052dd0400a1bdf5416d62b22cbd5e6e079c11a8cb984021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ab21e25b81ccd6e866391d85acb6ae93379895f61a4208a77a3623160fe3d7b 0.600000000000 1683079 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": 1196490, "vin": [ { "gen": { "height": 1196480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ab21e25b81ccd6e866391d85acb6ae93379895f61a4208a77a3623160fe3d7b" } } ], "extra": [ 1, 168, 158, 25, 71, 183, 36, 201, 221, 126, 65, 5, 45, 208, 64, 10, 27, 223, 84, 22, 214, 43, 34, 203, 213, 230, 224, 121, 193, 26, 140, 185, 132, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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