Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a38776b6d7130e654534b0140bc401a0b7ac4c37c4204a0d9190141232f08421

Tx prefix hash: f5705706d6166babf782dfc7b5f1592683fd7181fb56456d60f3eb5481ad1ab9
Tx public key: 63c9a995d099aeaf840ff79f2621e7e46250f2c9146ef21d22be6b8ca9a9816e
Timestamp: 1732739231 Timestamp [UCT]: 2024-11-27 20:27:11 Age [y:d:h:m:s]: 00:140:03:48:24
Block: 1163068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99988 RingCT/type: yes/0
Extra: 0163c9a995d099aeaf840ff79f2621e7e46250f2c9146ef21d22be6b8ca9a9816e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e59cfae09045666b0d53cfce8c70930f75ea879c784010c024d9f1ea4fcbd95 0.600000000000 1648733 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": 1163078, "vin": [ { "gen": { "height": 1163068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e59cfae09045666b0d53cfce8c70930f75ea879c784010c024d9f1ea4fcbd95" } } ], "extra": [ 1, 99, 201, 169, 149, 208, 153, 174, 175, 132, 15, 247, 159, 38, 33, 231, 228, 98, 80, 242, 201, 20, 110, 242, 29, 34, 190, 107, 140, 169, 169, 129, 110, 2, 17, 0, 0, 0, 5, 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