Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d53c9894b63b1208d2cc27046f261e6972104e4e91a468f9ae32437a389265

Tx prefix hash: 619041340e0e8817b45a0787d293bfeb7c168e8ad29b5cbbf4c122e3ad41f610
Tx public key: 7f03ee5c8fe5976d251e6c408c8267018b97f096fb7febfa13d009a39ab93b93
Timestamp: 1711393501 Timestamp [UCT]: 2024-03-25 19:05:01 Age [y:d:h:m:s]: 01:058:13:46:54
Block: 986225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302852 RingCT/type: yes/0
Extra: 017f03ee5c8fe5976d251e6c408c8267018b97f096fb7febfa13d009a39ab93b9302110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba25a3f3c565410a84765b90809c5efb0fe63f117caa824d77f052fd0bb2f429 0.600000000000 1446454 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": 986235, "vin": [ { "gen": { "height": 986225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba25a3f3c565410a84765b90809c5efb0fe63f117caa824d77f052fd0bb2f429" } } ], "extra": [ 1, 127, 3, 238, 92, 143, 229, 151, 109, 37, 30, 108, 64, 140, 130, 103, 1, 139, 151, 240, 150, 251, 127, 235, 250, 19, 208, 9, 163, 154, 185, 59, 147, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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