Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbac3c7abe1afd3a342245142ff75847e714f2cf046752764d9b5b9148979753

Tx prefix hash: 940d69f49c0d79b84cf765086b962be88c336fb1e8e06536b0a0cd5564e150c7
Tx public key: 8aa0febc558669faa4c1e15a983359a9fad2f8fa154173a0254eabbe17f14b8a
Timestamp: 1725219265 Timestamp [UCT]: 2024-09-01 19:34:25 Age [y:d:h:m:s]: 00:208:07:55:24
Block: 1100830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148731 RingCT/type: yes/0
Extra: 018aa0febc558669faa4c1e15a983359a9fad2f8fa154173a0254eabbe17f14b8a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4660e7f3dda7483c6cf4956062620ccaef2a29e87c9036b6cd046c95accc9c7 0.600000000000 1576811 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": 1100840, "vin": [ { "gen": { "height": 1100830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4660e7f3dda7483c6cf4956062620ccaef2a29e87c9036b6cd046c95accc9c7" } } ], "extra": [ 1, 138, 160, 254, 188, 85, 134, 105, 250, 164, 193, 225, 90, 152, 51, 89, 169, 250, 210, 248, 250, 21, 65, 115, 160, 37, 78, 171, 190, 23, 241, 75, 138, 2, 17, 0, 0, 0, 1, 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