Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f3c81ff7a898063b125bf81078b9cb2e816c50f7006fc3347d278d5f5d3261

Tx prefix hash: e732789fbbf5fb16a6a2d224e3229bff32e3d7b8936c34f519caba857317ec5c
Tx public key: 7d9097a40bb15f07df6124a6e6ba520a26604ed142810b05ebf72fab1558c63f
Timestamp: 1728599594 Timestamp [UCT]: 2024-10-10 22:33:14 Age [y:d:h:m:s]: 01:036:23:43:07
Block: 1128853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284817 RingCT/type: yes/0
Extra: 017d9097a40bb15f07df6124a6e6ba520a26604ed142810b05ebf72fab1558c63f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b604f3497376f600ba8eadd72f4a67b0117da4b96c6d3373fda10bab52d22d46 0.600000000000 1611676 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": 1128863, "vin": [ { "gen": { "height": 1128853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b604f3497376f600ba8eadd72f4a67b0117da4b96c6d3373fda10bab52d22d46" } } ], "extra": [ 1, 125, 144, 151, 164, 11, 177, 95, 7, 223, 97, 36, 166, 230, 186, 82, 10, 38, 96, 78, 209, 66, 129, 11, 5, 235, 247, 47, 171, 21, 88, 198, 63, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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