Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 232ca80738bbb3ee1625b577eb9d61bc76c71f2173df9314fd979d23d38889d4

Tx prefix hash: 4052adf027e14e6b828caa2fbd934d196d606e194dc398681dc440e26ade46ab
Tx public key: 44048aa58f0c391d635e0300cc44f1640b9c6b939f366d4408dd608a8b44d3ac
Timestamp: 1755151261 Timestamp [UCT]: 2025-08-14 06:01:01 Age [y:d:h:m:s]: 00:067:13:47:39
Block: 1346476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47808 RingCT/type: yes/0
Extra: 0144048aa58f0c391d635e0300cc44f1640b9c6b939f366d4408dd608a8b44d3ac021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f4fbe54ae5d8c6dd16074a9e231f23191f160826728838a2a309b4d110d3f53 0.600000000000 1834377 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": 1346486, "vin": [ { "gen": { "height": 1346476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f4fbe54ae5d8c6dd16074a9e231f23191f160826728838a2a309b4d110d3f53" } } ], "extra": [ 1, 68, 4, 138, 165, 143, 12, 57, 29, 99, 94, 3, 0, 204, 68, 241, 100, 11, 156, 107, 147, 159, 54, 109, 68, 8, 221, 96, 138, 139, 68, 211, 172, 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