Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e2c99d9adf920cb83a9f30a275b084e80594b24399e060593c0aaa07ea7deea

Tx prefix hash: 22f14436686ed641fc647146f76ef9175f427871efb521b79c90f1c00c104b84
Tx public key: 3d4a0e0929a93594a47d947ee9cfc9747a7840fe5b7898603d0aa1f8a51c4cd9
Timestamp: 1749433352 Timestamp [UCT]: 2025-06-09 01:42:32 Age [y:d:h:m:s]: 00:156:08:11:59
Block: 1301028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109405 RingCT/type: yes/0
Extra: 013d4a0e0929a93594a47d947ee9cfc9747a7840fe5b7898603d0aa1f8a51c4cd90211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee05edf8fe67bcbd02090ee0564c46c24e3a7d4a3525659cec74b7976b52d142 0.600000000000 1788581 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": 1301038, "vin": [ { "gen": { "height": 1301028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee05edf8fe67bcbd02090ee0564c46c24e3a7d4a3525659cec74b7976b52d142" } } ], "extra": [ 1, 61, 74, 14, 9, 41, 169, 53, 148, 164, 125, 148, 126, 233, 207, 201, 116, 122, 120, 64, 254, 91, 120, 152, 96, 61, 10, 161, 248, 165, 28, 76, 217, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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