Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87cfd9272f49415d7e481a672966edb318dfe7df7aa5c17f92c2f6231e0d2402

Tx prefix hash: 3acff24e5666c222ff80666e7b87866cd926710bcb5ff2b0c19a9519b5c137f1
Tx public key: ed5e429d1e426e3bc07b8cd0e5eb90c834de811539ba5948a88c39efdbd2e4af
Timestamp: 1731873854 Timestamp [UCT]: 2024-11-17 20:04:14 Age [y:d:h:m:s]: 00:134:21:37:31
Block: 1155913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96206 RingCT/type: yes/0
Extra: 01ed5e429d1e426e3bc07b8cd0e5eb90c834de811539ba5948a88c39efdbd2e4af021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd456ef78a9b4dc4da0d41e98cbbb10191a4686513d51751f624ff6768cf03e0 0.600000000000 1641532 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": 1155923, "vin": [ { "gen": { "height": 1155913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd456ef78a9b4dc4da0d41e98cbbb10191a4686513d51751f624ff6768cf03e0" } } ], "extra": [ 1, 237, 94, 66, 157, 30, 66, 110, 59, 192, 123, 140, 208, 229, 235, 144, 200, 52, 222, 129, 21, 57, 186, 89, 72, 168, 140, 57, 239, 219, 210, 228, 175, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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