Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eabd7aa05279ecc83b3ffc4576387015376e3c7d9ceea6b408880a1e9792b5bd

Tx prefix hash: 354372a897d791b43936e39cb2dfabe9752eced9d444cb5fd340aaf152b77a92
Tx public key: a2dd02108ad4b65ac3d256cdce3dcc0fef2cb5091e9016cff5e69e107623a77d
Timestamp: 1731334767 Timestamp [UCT]: 2024-11-11 14:19:27 Age [y:d:h:m:s]: 00:165:05:32:59
Block: 1151426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117945 RingCT/type: yes/0
Extra: 01a2dd02108ad4b65ac3d256cdce3dcc0fef2cb5091e9016cff5e69e107623a77d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 883afbbbdfad2dabab8e24f15cd15a7fb9a388784e84c9ca9683c1e45b81fd89 0.600000000000 1636951 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": 1151436, "vin": [ { "gen": { "height": 1151426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "883afbbbdfad2dabab8e24f15cd15a7fb9a388784e84c9ca9683c1e45b81fd89" } } ], "extra": [ 1, 162, 221, 2, 16, 138, 212, 182, 90, 195, 210, 86, 205, 206, 61, 204, 15, 239, 44, 181, 9, 30, 144, 22, 207, 245, 230, 158, 16, 118, 35, 167, 125, 2, 17, 0, 0, 0, 4, 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