Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad9feed00f095a83f4895ebe75d9e7335d83fa8ed786b5c98d28bc326c8a8e5

Tx prefix hash: c5f8522f717ddf42eb5881526e12d24f604d54495ccc95ba30242016b3df4bc6
Tx public key: 0454f53f819a44f0f5e96dee065e51243a3b72e59333050d2b1e202e92eac269
Timestamp: 1737530946 Timestamp [UCT]: 2025-01-22 07:29:06 Age [y:d:h:m:s]: 00:049:03:37:02
Block: 1202705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34945 RingCT/type: yes/0
Extra: 010454f53f819a44f0f5e96dee065e51243a3b72e59333050d2b1e202e92eac2690211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c0566ee7f070db2e8658229395f72392f7fb3560480dc63949693d826abd7f 0.600000000000 1689370 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": 1202715, "vin": [ { "gen": { "height": 1202705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c0566ee7f070db2e8658229395f72392f7fb3560480dc63949693d826abd7f" } } ], "extra": [ 1, 4, 84, 245, 63, 129, 154, 68, 240, 245, 233, 109, 238, 6, 94, 81, 36, 58, 59, 114, 229, 147, 51, 5, 13, 43, 30, 32, 46, 146, 234, 194, 105, 2, 17, 0, 0, 0, 3, 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