Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04baeb54719ea9de411762f764db3fec89e297024d5fb9ed3b8f63e27e18f35a

Tx prefix hash: b56a5cf43b3c64788a920953cd873d9e5a2c339005fcb21f50f7e1a8af5fde31
Tx public key: c34ad10a5a4e814936ac5c9741f9e437339a8b4fd719a954e5971f72c66c5861
Timestamp: 1749098664 Timestamp [UCT]: 2025-06-05 04:44:24 Age [y:d:h:m:s]: 00:159:03:16:58
Block: 1298249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111409 RingCT/type: yes/0
Extra: 01c34ad10a5a4e814936ac5c9741f9e437339a8b4fd719a954e5971f72c66c586102110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eefa7bb89b85931db3f80852dd3af71857cac0db14d2a67c5464426736f870b8 0.600000000000 1785772 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": 1298259, "vin": [ { "gen": { "height": 1298249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eefa7bb89b85931db3f80852dd3af71857cac0db14d2a67c5464426736f870b8" } } ], "extra": [ 1, 195, 74, 209, 10, 90, 78, 129, 73, 54, 172, 92, 151, 65, 249, 228, 55, 51, 154, 139, 79, 215, 25, 169, 84, 229, 151, 31, 114, 198, 108, 88, 97, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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