Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442ad4374ba544f2097466e28d9626706d3dcf4cfe82ea0ed508eb39644f14a6

Tx prefix hash: e3862695cd1aabf592077d1f8d9b9b99de9bd195825926b8080ec82e23c033af
Tx public key: bb9cd2a7a43c38a36c5e189425beb619a057785c939e0e1badadf7a40fa66525
Timestamp: 1711457696 Timestamp [UCT]: 2024-03-26 12:54:56 Age [y:d:h:m:s]: 01:013:07:18:06
Block: 986760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270446 RingCT/type: yes/0
Extra: 01bb9cd2a7a43c38a36c5e189425beb619a057785c939e0e1badadf7a40fa665250211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 761e509df4e35d2ff5350059b73463ecc4cfd1dd9cc7cab5e9644c590d67032f 0.600000000000 1446993 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": 986770, "vin": [ { "gen": { "height": 986760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "761e509df4e35d2ff5350059b73463ecc4cfd1dd9cc7cab5e9644c590d67032f" } } ], "extra": [ 1, 187, 156, 210, 167, 164, 60, 56, 163, 108, 94, 24, 148, 37, 190, 182, 25, 160, 87, 120, 92, 147, 158, 14, 27, 173, 173, 247, 164, 15, 166, 101, 37, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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