Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24048e40c83281025cd30a643fccf47d20aabb0d4aa927d4e51fb5b09b5032d4

Tx prefix hash: e9c00cdc7479bd5dfe26e6394962ee2f3f5f2ce4fec4282fc33ac301c5711ea7
Tx public key: 27c583d6ce3e5bae062e1e19435dc24d95da9e30c5d246495792f804384c1c59
Timestamp: 1763131767 Timestamp [UCT]: 2025-11-14 14:49:27 Age [y:d:h:m:s]: 00:038:18:10:41
Block: 1412015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27744 RingCT/type: yes/0
Extra: 0127c583d6ce3e5bae062e1e19435dc24d95da9e30c5d246495792f804384c1c59021100000005dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d28941f29f50a970808b2f364ed2f072a41c87b8daba9eb4dc2ade997b3aac7 0.600000000000 1900480 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": 1412025, "vin": [ { "gen": { "height": 1412015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d28941f29f50a970808b2f364ed2f072a41c87b8daba9eb4dc2ade997b3aac7" } } ], "extra": [ 1, 39, 197, 131, 214, 206, 62, 91, 174, 6, 46, 30, 25, 67, 93, 194, 77, 149, 218, 158, 48, 197, 210, 70, 73, 87, 146, 248, 4, 56, 76, 28, 89, 2, 17, 0, 0, 0, 5, 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