Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5acdc8673f49f84bbdeac877699a0f91dec2f003de8d6902c1cfee228f68d6d2

Tx prefix hash: 9bec420c43c66a2107548659afcc5d29c47456a78d17d2675b6e1ecf83f20c96
Tx public key: b6ff36b8b6c41d5dc15848872595df1c63a6c7add4a41c544e29361ee375a4d6
Timestamp: 1729146268 Timestamp [UCT]: 2024-10-17 06:24:28 Age [y:d:h:m:s]: 00:195:18:49:12
Block: 1133389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139708 RingCT/type: yes/0
Extra: 01b6ff36b8b6c41d5dc15848872595df1c63a6c7add4a41c544e29361ee375a4d602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 872416dd8d43011528fb3b628ea873bb83c10132adf755ef055c1368a91ae38e 0.600000000000 1616498 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": 1133399, "vin": [ { "gen": { "height": 1133389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "872416dd8d43011528fb3b628ea873bb83c10132adf755ef055c1368a91ae38e" } } ], "extra": [ 1, 182, 255, 54, 184, 182, 196, 29, 93, 193, 88, 72, 135, 37, 149, 223, 28, 99, 166, 199, 173, 212, 164, 28, 84, 78, 41, 54, 30, 227, 117, 164, 214, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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