Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b19d1453acfa76f9473c3a480bd7eae1a1e44b412064dcc43f461ce9c65a880

Tx prefix hash: a525888258fd1703f219dd5d9fa3b0d2bf94d31560dcabbd4d92c2e3a3a5ce26
Tx public key: 376634e6e5ed04194df2c452346cb462f0099954e25221e007c93d119413ab8b
Timestamp: 1754906644 Timestamp [UCT]: 2025-08-11 10:04:04 Age [y:d:h:m:s]: 00:108:19:47:11
Block: 1344735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77034 RingCT/type: yes/0
Extra: 01376634e6e5ed04194df2c452346cb462f0099954e25221e007c93d119413ab8b021100000008b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66e3cd8de26e7fc45156550379d68cf54f662d2dca60764af2fa921e35f1d845 0.600000000000 1832620 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": 1344745, "vin": [ { "gen": { "height": 1344735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66e3cd8de26e7fc45156550379d68cf54f662d2dca60764af2fa921e35f1d845" } } ], "extra": [ 1, 55, 102, 52, 230, 229, 237, 4, 25, 77, 242, 196, 82, 52, 108, 180, 98, 240, 9, 153, 84, 226, 82, 33, 224, 7, 201, 61, 17, 148, 19, 171, 139, 2, 17, 0, 0, 0, 8, 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