Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b392e293ccc550e8b1f8d1f08a6caf08ca40c9dd0d0d6361dbdae04be257c27a

Tx prefix hash: 4af0b34d94e1f8a9f4a9848eed1048e1fddeb756449670e78c52b845c8a169ad
Tx public key: dd73777bfd658f544c78d16abbe5e394f618766993ebdf831f70ec283f150272
Timestamp: 1737877486 Timestamp [UCT]: 2025-01-26 07:44:46 Age [y:d:h:m:s]: 00:047:08:06:13
Block: 1205569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33659 RingCT/type: yes/0
Extra: 01dd73777bfd658f544c78d16abbe5e394f618766993ebdf831f70ec283f150272021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fba7ae292eac4c35a8356ebcb3e716358931b3781c5c6e1fe1e6aa791e6c70e 0.600000000000 1692266 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": 1205579, "vin": [ { "gen": { "height": 1205569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fba7ae292eac4c35a8356ebcb3e716358931b3781c5c6e1fe1e6aa791e6c70e" } } ], "extra": [ 1, 221, 115, 119, 123, 253, 101, 143, 84, 76, 120, 209, 106, 187, 229, 227, 148, 246, 24, 118, 105, 147, 235, 223, 131, 31, 112, 236, 40, 63, 21, 2, 114, 2, 17, 0, 0, 0, 1, 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