Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c2287c37ab1382117cc5e8df7faaada0d5ccb3a2cd4099624489eb2e568121

Tx prefix hash: 2cd084d647c306ee22ff4e2041f85dcae58af71753605d2c68bb33a1ac8386c6
Tx public key: abd5b24a1e7bf5f00d61efabd34a196bf88cfa266c50d9b16869cf41ed8d1f14
Timestamp: 1704913153 Timestamp [UCT]: 2024-01-10 18:59:13 Age [y:d:h:m:s]: 01:098:15:24:08
Block: 932465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331614 RingCT/type: yes/0
Extra: 01abd5b24a1e7bf5f00d61efabd34a196bf88cfa266c50d9b16869cf41ed8d1f140211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0e7047c218cab1588af914830e23062f8e63fb84609d007552baea934f64199 0.600000000000 1390401 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": 932475, "vin": [ { "gen": { "height": 932465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0e7047c218cab1588af914830e23062f8e63fb84609d007552baea934f64199" } } ], "extra": [ 1, 171, 213, 178, 74, 30, 123, 245, 240, 13, 97, 239, 171, 211, 74, 25, 107, 248, 140, 250, 38, 108, 80, 217, 177, 104, 105, 207, 65, 237, 141, 31, 20, 2, 17, 0, 0, 0, 3, 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