Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45b8bc127c52bae7244dd559b835c6dd9a159ed306012e3bdd73928dd7c8ed15

Tx prefix hash: 07ac062eee668ba83ff51a0205279e4d95e71cea797df0c06db6241cc8402f9c
Tx public key: f95bb8f81f7afbb71896e21a38f0a29fdd4d2865d50e4dcbf0b5811bb5036cb7
Timestamp: 1754653588 Timestamp [UCT]: 2025-08-08 11:46:28 Age [y:d:h:m:s]: 00:058:11:36:19
Block: 1342786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40828 RingCT/type: yes/0
Extra: 01f95bb8f81f7afbb71896e21a38f0a29fdd4d2865d50e4dcbf0b5811bb5036cb7021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a88b9101ef1707030201ced4e5ffa8dbb355092ade2c6d7a5b7a45feb570b17 0.600000000000 1830619 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": 1342796, "vin": [ { "gen": { "height": 1342786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a88b9101ef1707030201ced4e5ffa8dbb355092ade2c6d7a5b7a45feb570b17" } } ], "extra": [ 1, 249, 91, 184, 248, 31, 122, 251, 183, 24, 150, 226, 26, 56, 240, 162, 159, 221, 77, 40, 101, 213, 14, 77, 203, 240, 181, 129, 27, 181, 3, 108, 183, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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