Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 358ce934b656d53b0af8d208f278bacc9eb53924ae37e0a9e56c7e83a88e6e8e

Tx prefix hash: 26c515cb80905a0dd947ef3607019abc9b470ce8c436e5088abe7526e60388a6
Tx public key: 483edfc84d8bf153a256b3b96d802e06328e5aa767e6908dc1c008160254d5a0
Timestamp: 1750121047 Timestamp [UCT]: 2025-06-17 00:44:07 Age [y:d:h:m:s]: 00:157:22:28:08
Block: 1306604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110664 RingCT/type: yes/0
Extra: 01483edfc84d8bf153a256b3b96d802e06328e5aa767e6908dc1c008160254d5a0021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d131b9fcc1840537925a2d554ad2c45fffe531ea98f20b3992029aa459d0a06 0.600000000000 1794211 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": 1306614, "vin": [ { "gen": { "height": 1306604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d131b9fcc1840537925a2d554ad2c45fffe531ea98f20b3992029aa459d0a06" } } ], "extra": [ 1, 72, 62, 223, 200, 77, 139, 241, 83, 162, 86, 179, 185, 109, 128, 46, 6, 50, 142, 90, 167, 103, 230, 144, 141, 193, 192, 8, 22, 2, 84, 213, 160, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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