Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84f19b98701b8d9185c703081b6dda2d2dc926524fc0ecdbd33c56de6994dfbb

Tx prefix hash: f588ab57b84bbe8ce207cd0b3b753fcb5f988487e03f7b84c80e7aa2b2ce0c91
Tx public key: 011135d6a095e96ec6e5a82895b4edaead011fffc00b9caf69aaa39f292ddc5e
Timestamp: 1755874695 Timestamp [UCT]: 2025-08-22 14:58:15 Age [y:d:h:m:s]: 00:090:15:15:39
Block: 1352053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64698 RingCT/type: yes/0
Extra: 01011135d6a095e96ec6e5a82895b4edaead011fffc00b9caf69aaa39f292ddc5e021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8be93fd6fc075233c79d0a43df2f2864f26b471ff6b085a8d50043b0c55fc9e5 0.600000000000 1840014 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": 1352063, "vin": [ { "gen": { "height": 1352053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8be93fd6fc075233c79d0a43df2f2864f26b471ff6b085a8d50043b0c55fc9e5" } } ], "extra": [ 1, 1, 17, 53, 214, 160, 149, 233, 110, 198, 229, 168, 40, 149, 180, 237, 174, 173, 1, 31, 255, 192, 11, 156, 175, 105, 170, 163, 159, 41, 45, 220, 94, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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