Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49aee19061d8009d44463e8f837a547e4393bd62d03ca630e2e9dd2d4158ec6

Tx prefix hash: 9a0b41b73695d4b0055454a81f1674705ae706998d51a9be386dcf24e25e42a1
Tx public key: 675364f3c71dcc6abc812e7f35cb716f794cf3c5bb29a705a0b0063bf3ea429c
Timestamp: 1721388299 Timestamp [UCT]: 2024-07-19 11:24:59 Age [y:d:h:m:s]: 00:260:09:13:22
Block: 1069079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186002 RingCT/type: yes/0
Extra: 01675364f3c71dcc6abc812e7f35cb716f794cf3c5bb29a705a0b0063bf3ea429c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d13b01d4a4585ee9a4135e74a18ac2bcbce21ab834991546afbbeb0bf10076ea 0.600000000000 1540362 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": 1069089, "vin": [ { "gen": { "height": 1069079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d13b01d4a4585ee9a4135e74a18ac2bcbce21ab834991546afbbeb0bf10076ea" } } ], "extra": [ 1, 103, 83, 100, 243, 199, 29, 204, 106, 188, 129, 46, 127, 53, 203, 113, 111, 121, 76, 243, 197, 187, 41, 167, 5, 160, 176, 6, 59, 243, 234, 66, 156, 2, 17, 0, 0, 0, 5, 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