Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733244c194a05ded11c961473fedb68080782567111b084bf3592f8c06eec721

Tx prefix hash: c291740d05846e104182803c7c2f6b5fc0b3f93550f8a41c261528cd3cd5107e
Tx public key: a48600a03e49910fc31c0880fcd97e6cee90f1d665c5283efdc337ad57af7a0f
Timestamp: 1754889855 Timestamp [UCT]: 2025-08-11 05:24:15 Age [y:d:h:m:s]: 00:048:13:50:37
Block: 1344609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33874 RingCT/type: yes/0
Extra: 01a48600a03e49910fc31c0880fcd97e6cee90f1d665c5283efdc337ad57af7a0f021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fac8b131a3b301daf88ddd9d167d6ef8e33b5f6976c9cdb2f679e8b1b1f0efb 0.600000000000 1832494 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": 1344619, "vin": [ { "gen": { "height": 1344609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fac8b131a3b301daf88ddd9d167d6ef8e33b5f6976c9cdb2f679e8b1b1f0efb" } } ], "extra": [ 1, 164, 134, 0, 160, 62, 73, 145, 15, 195, 28, 8, 128, 252, 217, 126, 108, 238, 144, 241, 214, 101, 197, 40, 62, 253, 195, 55, 173, 87, 175, 122, 15, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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