Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da0e9c7eea818c2ee1c0e58959455d7f15b77c7302157bbb37c50086c43034de

Tx prefix hash: e4814491f12be287c6d8ecc3a906e9126550fb0c09e196eaff65020070eb7093
Tx public key: 1b74952ea92622ed1c91966e2a68882b6c907230a86766f8f0a7a036583ea1d5
Timestamp: 1733202879 Timestamp [UCT]: 2024-12-03 05:14:39 Age [y:d:h:m:s]: 00:126:03:34:08
Block: 1166913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89950 RingCT/type: yes/0
Extra: 011b74952ea92622ed1c91966e2a68882b6c907230a86766f8f0a7a036583ea1d50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6792af6fbf6471f1ffa5b0b7270aad4cb49c18fd6891ed224cccd99908b6e062 0.600000000000 1652606 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": 1166923, "vin": [ { "gen": { "height": 1166913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6792af6fbf6471f1ffa5b0b7270aad4cb49c18fd6891ed224cccd99908b6e062" } } ], "extra": [ 1, 27, 116, 149, 46, 169, 38, 34, 237, 28, 145, 150, 110, 42, 104, 136, 43, 108, 144, 114, 48, 168, 103, 102, 248, 240, 167, 160, 54, 88, 62, 161, 213, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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