Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a08edbb684358595e7cddb1c04893886e95cc87e0b4254bf0d70ea19c9f6f3a

Tx prefix hash: 283ee8dc74e1a960bb6a29609d7e8c7c6c364564e8bb1da984e6452f1b453e57
Tx public key: 59a478a7a570ca71fbf9f77e04a9550c75704a12cf199b1d753d79b933245392
Timestamp: 1737139724 Timestamp [UCT]: 2025-01-17 18:48:44 Age [y:d:h:m:s]: 00:152:18:38:52
Block: 1199501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108892 RingCT/type: yes/0
Extra: 0159a478a7a570ca71fbf9f77e04a9550c75704a12cf199b1d753d79b9332453920211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a5bd10094a80232b6dabcf35a018ce9cb55ef878dc387db0592847b2e0aea3b 0.600000000000 1686132 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": 1199511, "vin": [ { "gen": { "height": 1199501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a5bd10094a80232b6dabcf35a018ce9cb55ef878dc387db0592847b2e0aea3b" } } ], "extra": [ 1, 89, 164, 120, 167, 165, 112, 202, 113, 251, 249, 247, 126, 4, 169, 85, 12, 117, 112, 74, 18, 207, 25, 155, 29, 117, 61, 121, 185, 51, 36, 83, 146, 2, 17, 0, 0, 0, 3, 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