Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef9563fbd4a980e819f6b7ee7f25ee33c93d883cfe3ac9f3c646cbe7507d8fed

Tx prefix hash: 086f3f96355c6742e6b54229243a6e579727c0004848ae973f6bc89a36d50b8e
Tx public key: 2ba5405837be8529748bc3ccbc0a30cb2ed7d72725785c187bbb50526bd1c058
Timestamp: 1721724142 Timestamp [UCT]: 2024-07-23 08:42:22 Age [y:d:h:m:s]: 01:110:16:42:42
Block: 1071841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337617 RingCT/type: yes/0
Extra: 012ba5405837be8529748bc3ccbc0a30cb2ed7d72725785c187bbb50526bd1c058021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6c0bc7474f1756f3fb20cef1f6449f2e385941aa75e02d4939f7ee5d222dc3e 0.600000000000 1544220 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": 1071851, "vin": [ { "gen": { "height": 1071841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6c0bc7474f1756f3fb20cef1f6449f2e385941aa75e02d4939f7ee5d222dc3e" } } ], "extra": [ 1, 43, 165, 64, 88, 55, 190, 133, 41, 116, 139, 195, 204, 188, 10, 48, 203, 46, 215, 215, 39, 37, 120, 92, 24, 123, 187, 80, 82, 107, 209, 192, 88, 2, 17, 0, 0, 0, 4, 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