Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: defcd54829464a92b49c306e33478c7517718cff1852609f1049e77a8a3049f8

Tx prefix hash: b658449245194a94f50e7b53919e328013d986e59d905721ac09d40faca1fa1a
Tx public key: f0e54d5fd7dc56bf7721f3645d420f5c8aecf8fa24594b4990428ab037ce1296
Timestamp: 1709112715 Timestamp [UCT]: 2024-02-28 09:31:55 Age [y:d:h:m:s]: 01:016:07:34:43
Block: 967302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272677 RingCT/type: yes/0
Extra: 01f0e54d5fd7dc56bf7721f3645d420f5c8aecf8fa24594b4990428ab037ce12960211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e55e510f1d22acaf36236552f69908fdac6be31cb634a9a8785e2e9fcc42b7fb 0.600000000000 1427079 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": 967312, "vin": [ { "gen": { "height": 967302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e55e510f1d22acaf36236552f69908fdac6be31cb634a9a8785e2e9fcc42b7fb" } } ], "extra": [ 1, 240, 229, 77, 95, 215, 220, 86, 191, 119, 33, 243, 100, 93, 66, 15, 92, 138, 236, 248, 250, 36, 89, 75, 73, 144, 66, 138, 176, 55, 206, 18, 150, 2, 17, 0, 0, 0, 5, 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