Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d41c8b70e84786cbd149a6e1715349137dfc5e3e5e0b145fdbc2c32450fe3f0

Tx prefix hash: 0945d58ae992f08b434501d4a4d4aef48a30d056970335ac1348582999b5ca0c
Tx public key: 6b954c36e61121845f8f63d98060057cadc4477ab8114ae9330dd29f8b8fb0e0
Timestamp: 1682524360 Timestamp [UCT]: 2023-04-26 15:52:40 Age [y:d:h:m:s]: 01:347:20:12:29
Block: 747113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509849 RingCT/type: yes/0
Extra: 016b954c36e61121845f8f63d98060057cadc4477ab8114ae9330dd29f8b8fb0e0021100000007faf35c9c000000000000000000

1 output(s) for total of 2.053547236000 dcy

stealth address amount amount idx
00: 61d938efa81934fdad71b539fe86664c37efd9a01c1291c9b02d60d7a48916ab 2.053547236000 1194750 of 0

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": 747123, "vin": [ { "gen": { "height": 747113 } } ], "vout": [ { "amount": 2053547236, "target": { "key": "61d938efa81934fdad71b539fe86664c37efd9a01c1291c9b02d60d7a48916ab" } } ], "extra": [ 1, 107, 149, 76, 54, 230, 17, 33, 132, 95, 143, 99, 217, 128, 96, 5, 124, 173, 196, 71, 122, 184, 17, 74, 233, 51, 13, 210, 159, 139, 143, 176, 224, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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