Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f5ed93d8f8ea79f767d6e2df7c562c49884f230227fadd4adc54d4bb97c669

Tx prefix hash: 0d5b43e6f5c5bd72a72b902834b5a1a2225dad5b2fd3953396036368f2283cc2
Tx public key: 6387e8cc93ade5b0945b3c40c05d368f512383cd0ede79932d220fcf46b5bd6a
Timestamp: 1721984001 Timestamp [UCT]: 2024-07-26 08:53:21 Age [y:d:h:m:s]: 00:241:10:19:04
Block: 1074005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172447 RingCT/type: yes/0
Extra: 016387e8cc93ade5b0945b3c40c05d368f512383cd0ede79932d220fcf46b5bd6a021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6a1a8ced5a0a85285815e2cee37c0044220c9beced4e389c17744bfd55fd38c 0.600000000000 1546514 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": 1074015, "vin": [ { "gen": { "height": 1074005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6a1a8ced5a0a85285815e2cee37c0044220c9beced4e389c17744bfd55fd38c" } } ], "extra": [ 1, 99, 135, 232, 204, 147, 173, 229, 176, 148, 91, 60, 64, 192, 93, 54, 143, 81, 35, 131, 205, 14, 222, 121, 147, 45, 34, 15, 207, 70, 181, 189, 106, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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