Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ad55bc8b322d075c618683b745f403f2688d64124984dc1b6c5ac553d98491

Tx prefix hash: f8b35770b11fedf9c25c15a9004b826ce5af8c685ca0f11c357072a4f9406af7
Tx public key: 6ae11945f452f4c16069fb267e6485d40015bba0f4c4f04289c0a30ec7acb64c
Timestamp: 1737657610 Timestamp [UCT]: 2025-01-23 18:40:10 Age [y:d:h:m:s]: 00:331:10:51:31
Block: 1203749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234482 RingCT/type: yes/0
Extra: 016ae11945f452f4c16069fb267e6485d40015bba0f4c4f04289c0a30ec7acb64c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e57c80dbec98200e0c47fc9446e06c784a30faf7fdb62914dee6167d4832b6e3 0.600000000000 1690428 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": 1203759, "vin": [ { "gen": { "height": 1203749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e57c80dbec98200e0c47fc9446e06c784a30faf7fdb62914dee6167d4832b6e3" } } ], "extra": [ 1, 106, 225, 25, 69, 244, 82, 244, 193, 96, 105, 251, 38, 126, 100, 133, 212, 0, 21, 187, 160, 244, 196, 240, 66, 137, 192, 163, 14, 199, 172, 182, 76, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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