Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ed6ab6842d769113b3d9749787d67267d176dc63e9db120be9191d67f8b614

Tx prefix hash: a674e895895db75fdea33c35dbe3b7e5c4ebc30a5c8e3e77ca99afb22e3d0f05
Tx public key: 9c9b485dd7053ab0ecbd21ed25b423c4545299ee14d9c61b77bcc7ca1f2cbe35
Timestamp: 1735062415 Timestamp [UCT]: 2024-12-24 17:46:55 Age [y:d:h:m:s]: 00:037:08:27:05
Block: 1182327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26437 RingCT/type: yes/0
Extra: 019c9b485dd7053ab0ecbd21ed25b423c4545299ee14d9c61b77bcc7ca1f2cbe35021100000003fb9ebda4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37468444acaf09b0d5eb8f8060e7a52277283a8d621b80d10040756efc67d69b 0.600000000000 1668760 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": 1182337, "vin": [ { "gen": { "height": 1182327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37468444acaf09b0d5eb8f8060e7a52277283a8d621b80d10040756efc67d69b" } } ], "extra": [ 1, 156, 155, 72, 93, 215, 5, 58, 176, 236, 189, 33, 237, 37, 180, 35, 196, 84, 82, 153, 238, 20, 217, 198, 27, 119, 188, 199, 202, 31, 44, 190, 53, 2, 17, 0, 0, 0, 3, 251, 158, 189, 164, 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