Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db46ff95a5c772e91cc8ddfee31ad522c88e18470dd2e7236b25a5ec99e514ec

Tx prefix hash: 321b0609679883d8294c632ff5550615c5bdd103dfd73835b350916c45b15e82
Tx public key: a72f79e7aac2646c358a58e8ecd1f2e5b22ebee6ac4d4ffe8a4f2b975cecb330
Timestamp: 1740716074 Timestamp [UCT]: 2025-02-28 04:14:34 Age [y:d:h:m:s]: 00:266:20:07:26
Block: 1228832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188473 RingCT/type: yes/0
Extra: 01a72f79e7aac2646c358a58e8ecd1f2e5b22ebee6ac4d4ffe8a4f2b975cecb330021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29d0467422ac0074e76de770b1a9c8f6c38131a09f4d162bfc571d03fed5b51a 0.600000000000 1715713 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": 1228842, "vin": [ { "gen": { "height": 1228832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29d0467422ac0074e76de770b1a9c8f6c38131a09f4d162bfc571d03fed5b51a" } } ], "extra": [ 1, 167, 47, 121, 231, 170, 194, 100, 108, 53, 138, 88, 232, 236, 209, 242, 229, 178, 46, 190, 230, 172, 77, 79, 254, 138, 79, 43, 151, 92, 236, 179, 48, 2, 17, 0, 0, 0, 4, 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