Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04c4054897b3e98ab97e9fe4d756caa1547e55c130231f071dbd586df47c140a

Tx prefix hash: d0c38c06f6385347c4617ce1ac9f9a30d6c0b76ebb0170eda8a6dbc26254577c
Tx public key: 043d2149b341038fb77b7edb0ba1efa54b973aaf7c07a20f73c4864dd4642441
Timestamp: 1716234566 Timestamp [UCT]: 2024-05-20 19:49:26 Age [y:d:h:m:s]: 00:234:20:29:33
Block: 1026341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168077 RingCT/type: yes/0
Extra: 01043d2149b341038fb77b7edb0ba1efa54b973aaf7c07a20f73c4864dd46424410211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ada9dc810aac4c20e021e8918df252cfc9a86d3f90089e106dc88588b6f40d25 0.600000000000 1493372 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": 1026351, "vin": [ { "gen": { "height": 1026341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ada9dc810aac4c20e021e8918df252cfc9a86d3f90089e106dc88588b6f40d25" } } ], "extra": [ 1, 4, 61, 33, 73, 179, 65, 3, 143, 183, 123, 126, 219, 11, 161, 239, 165, 75, 151, 58, 175, 124, 7, 162, 15, 115, 196, 134, 77, 212, 100, 36, 65, 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