Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa2b1e67db1e3e8033db78952500de630c4ccb855f210e8efe466907374fd748

Tx prefix hash: 3208eb3f87828e7071c295b3f2825094c17c84e7fd1b4b567af2337c388368d0
Tx public key: e7057f3ad8d1dc2c346554ffe009b8bb0aa036e472934b3497034e9c6461023e
Timestamp: 1735064163 Timestamp [UCT]: 2024-12-24 18:16:03 Age [y:d:h:m:s]: 00:121:08:31:03
Block: 1182335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86528 RingCT/type: yes/0
Extra: 01e7057f3ad8d1dc2c346554ffe009b8bb0aa036e472934b3497034e9c6461023e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99d56fc2631b1e1a3c4980633f033ee4a7e1a2dbfe4d1dbb111229324daae080 0.600000000000 1668768 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": 1182345, "vin": [ { "gen": { "height": 1182335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99d56fc2631b1e1a3c4980633f033ee4a7e1a2dbfe4d1dbb111229324daae080" } } ], "extra": [ 1, 231, 5, 127, 58, 216, 209, 220, 44, 52, 101, 84, 255, 224, 9, 184, 187, 10, 160, 54, 228, 114, 147, 75, 52, 151, 3, 78, 156, 100, 97, 2, 62, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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