Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fefc05c21386795a6b7a6eae1d6e34f6e899f91745ed3e5ac2bd6343d2519285

Tx prefix hash: 02abc40b333e1deea2419649081505679a747eab81b7ed883f4722e32d5a10bb
Tx public key: 9d91d100dc94e42792afc4e0513fd9bdd8ddc351d2e5b615057112c69c2d3422
Timestamp: 1728423176 Timestamp [UCT]: 2024-10-08 21:32:56 Age [y:d:h:m:s]: 01:040:20:17:33
Block: 1127375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287597 RingCT/type: yes/0
Extra: 019d91d100dc94e42792afc4e0513fd9bdd8ddc351d2e5b615057112c69c2d3422021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e5f22bf3fb179c82e1a369618bde7d8697969f37716070fe7e6522eb4f142d6 0.600000000000 1610180 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": 1127385, "vin": [ { "gen": { "height": 1127375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e5f22bf3fb179c82e1a369618bde7d8697969f37716070fe7e6522eb4f142d6" } } ], "extra": [ 1, 157, 145, 209, 0, 220, 148, 228, 39, 146, 175, 196, 224, 81, 63, 217, 189, 216, 221, 195, 81, 210, 229, 182, 21, 5, 113, 18, 198, 156, 45, 52, 34, 2, 17, 0, 0, 0, 4, 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