Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffab7e3bf01e8e087fbd2aa499bea3002e391de4272157776806387f9c80a25c

Tx prefix hash: 11ae213c57027c2b5db4628e47c788f6c58ec9b73109edf2a06959cd75739e7b
Tx public key: d9add4d3df95591df806669aeeec7764c47064032a84c6816fc1a33d7b738972
Timestamp: 1766014041 Timestamp [UCT]: 2025-12-17 23:27:21 Age [y:d:h:m:s]: 00:005:12:59:46
Block: 1435889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3969 RingCT/type: yes/0
Extra: 01d9add4d3df95591df806669aeeec7764c47064032a84c6816fc1a33d7b738972021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b59452a9706e92bd23a07a15b9f523e02e0b6c82a543c986830466d084601863 0.600000000000 1924694 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": 1435899, "vin": [ { "gen": { "height": 1435889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b59452a9706e92bd23a07a15b9f523e02e0b6c82a543c986830466d084601863" } } ], "extra": [ 1, 217, 173, 212, 211, 223, 149, 89, 29, 248, 6, 102, 154, 238, 236, 119, 100, 196, 112, 100, 3, 42, 132, 198, 129, 111, 193, 163, 61, 123, 115, 137, 114, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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