Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3863fda0e31b9239c3256fca733848fb4ed077cb6cd26bc9a42ea1dd15ec008f

Tx prefix hash: b1607b7114c3e9a0fb5f54a67b5cd6ab389f93774dcc1dffa6f5a09f89eede6b
Tx public key: 4413bd40b5d543d0b9c3f7653973c5f6ef49838a556b6af9013abb167eb95340
Timestamp: 1682511206 Timestamp [UCT]: 2023-04-26 12:13:26 Age [y:d:h:m:s]: 02:051:14:44:02
Block: 747001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558969 RingCT/type: yes/0
Extra: 014413bd40b5d543d0b9c3f7653973c5f6ef49838a556b6af9013abb167eb9534002110000000575e3f0e9000000000000000000

1 output(s) for total of 2.055302733000 dcy

stealth address amount amount idx
00: 8b95f2f710281c0cf1bd386a97cfd18c1ff7aff45c2195bc46c8a0d3a3c6dbb4 2.055302733000 1194626 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": 747011, "vin": [ { "gen": { "height": 747001 } } ], "vout": [ { "amount": 2055302733, "target": { "key": "8b95f2f710281c0cf1bd386a97cfd18c1ff7aff45c2195bc46c8a0d3a3c6dbb4" } } ], "extra": [ 1, 68, 19, 189, 64, 181, 213, 67, 208, 185, 195, 247, 101, 57, 115, 197, 246, 239, 73, 131, 138, 85, 107, 106, 249, 1, 58, 187, 22, 126, 185, 83, 64, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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