Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 135963ae3d6dc952c4ea258c1e13bcb59f506c114d3f1f6ed9281f4c28b8972b

Tx prefix hash: 9b0045ab02e0dbfcc65540fd350bb142a01b0e37333e6ac3cb024c4efa6726c6
Tx public key: ba6b1e06d43cc89dbf6f66246841dc91f8dde030307616927568de8c08676372
Timestamp: 1716054083 Timestamp [UCT]: 2024-05-18 17:41:23 Age [y:d:h:m:s]: 00:237:02:40:23
Block: 1024841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169705 RingCT/type: yes/0
Extra: 01ba6b1e06d43cc89dbf6f66246841dc91f8dde030307616927568de8c0867637202110000000352d47e94000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: a91b16af662067dfc00147aaa1e1d1cb1fdcdcfcbda2f65d9caa58fe1d1c6ade 0.615600000000 1490904 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": 1024851, "vin": [ { "gen": { "height": 1024841 } } ], "vout": [ { "amount": 615600000, "target": { "key": "a91b16af662067dfc00147aaa1e1d1cb1fdcdcfcbda2f65d9caa58fe1d1c6ade" } } ], "extra": [ 1, 186, 107, 30, 6, 212, 60, 200, 157, 191, 111, 102, 36, 104, 65, 220, 145, 248, 221, 224, 48, 48, 118, 22, 146, 117, 104, 222, 140, 8, 103, 99, 114, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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