Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff1a668e0385e6ad4aa285391179efc6e834bcc89d3d44eb96b75d7313e7c86

Tx prefix hash: afb0013ce489a846531d92690f6694a05af3a4ba1816be83b67ecff252da9d1d
Tx public key: f936e52ada7302b671df0d80ff020e78a8c42f1bb6d82cbc5ab23e33e179ee9c
Timestamp: 1734167044 Timestamp [UCT]: 2024-12-14 09:04:04 Age [y:d:h:m:s]: 00:109:14:58:40
Block: 1174912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78115 RingCT/type: yes/0
Extra: 01f936e52ada7302b671df0d80ff020e78a8c42f1bb6d82cbc5ab23e33e179ee9c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4132c96e42e02c1891d0f70858f6d1b7c45d7c8eb0c48072007eb2af4269a6fa 0.600000000000 1661123 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": 1174922, "vin": [ { "gen": { "height": 1174912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4132c96e42e02c1891d0f70858f6d1b7c45d7c8eb0c48072007eb2af4269a6fa" } } ], "extra": [ 1, 249, 54, 229, 42, 218, 115, 2, 182, 113, 223, 13, 128, 255, 2, 14, 120, 168, 196, 47, 27, 182, 216, 44, 188, 90, 178, 62, 51, 225, 121, 238, 156, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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