Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0970d1daab1e1c47cef031571fd58bd1c3ac34b54b264032fb1a9830f751825

Tx prefix hash: 514835ab6e796b2c4066c80b2ec8333bbf17962994c15f9672d634e35aca2f24
Tx public key: 5dbb710799e635bdf904422796fd1ba65ad338b6b3f975b08faf5da9cb8d4c47
Timestamp: 1723621448 Timestamp [UCT]: 2024-08-14 07:44:08 Age [y:d:h:m:s]: 00:297:03:17:29
Block: 1087578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212293 RingCT/type: yes/0
Extra: 015dbb710799e635bdf904422796fd1ba65ad338b6b3f975b08faf5da9cb8d4c47021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 061f58316f36ad328660154e8bc43bb49e2957091fb61082696e26c1ff53a5db 0.600000000000 1562187 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": 1087588, "vin": [ { "gen": { "height": 1087578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "061f58316f36ad328660154e8bc43bb49e2957091fb61082696e26c1ff53a5db" } } ], "extra": [ 1, 93, 187, 113, 7, 153, 230, 53, 189, 249, 4, 66, 39, 150, 253, 27, 166, 90, 211, 56, 182, 179, 249, 117, 176, 143, 175, 93, 169, 203, 141, 76, 71, 2, 17, 0, 0, 0, 6, 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