Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c0a657a63c74014248750a535fc73c38fb502fce1c7ef816488e0adf16d805

Tx prefix hash: 3eea3c6ed3c0aa28dd9f5b15d8f898873375b43e4c4bfb9cd42d5dbbd2134e37
Tx public key: b99091af679e1494d4ea4c57565bcce92fec58e0ebf45e3c48e2124819f7f654
Timestamp: 1734866473 Timestamp [UCT]: 2024-12-22 11:21:13 Age [y:d:h:m:s]: 00:091:15:50:50
Block: 1180718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65254 RingCT/type: yes/0
Extra: 01b99091af679e1494d4ea4c57565bcce92fec58e0ebf45e3c48e2124819f7f6540211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a84a863bacc6f633adbb57c2c943a54e44889c3be57d0db68c6f589beb60b7c 0.600000000000 1667131 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": 1180728, "vin": [ { "gen": { "height": 1180718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a84a863bacc6f633adbb57c2c943a54e44889c3be57d0db68c6f589beb60b7c" } } ], "extra": [ 1, 185, 144, 145, 175, 103, 158, 20, 148, 212, 234, 76, 87, 86, 91, 204, 233, 47, 236, 88, 224, 235, 244, 94, 60, 72, 226, 18, 72, 25, 247, 246, 84, 2, 17, 0, 0, 0, 9, 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