Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa05b53adc75f5d1050dd516bef019f73615fa74318ca26ff2f4a525a19f6a7

Tx prefix hash: 8baeb991601a6a2597416c08804fe7283db560fc24ec6438b00be38590b88202
Tx public key: dd479a9a7d53b2b5798d5b4907c4fddffa8eed690c54219d41769a90a4dbeaeb
Timestamp: 1721448593 Timestamp [UCT]: 2024-07-20 04:09:53 Age [y:d:h:m:s]: 00:257:20:52:05
Block: 1069604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184180 RingCT/type: yes/0
Extra: 01dd479a9a7d53b2b5798d5b4907c4fddffa8eed690c54219d41769a90a4dbeaeb021100000003162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc752b2303b5d1f4952aa9749fe499c1adb01aac2311028840b4ae1aab0b2bc1 0.600000000000 1541085 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": 1069614, "vin": [ { "gen": { "height": 1069604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc752b2303b5d1f4952aa9749fe499c1adb01aac2311028840b4ae1aab0b2bc1" } } ], "extra": [ 1, 221, 71, 154, 154, 125, 83, 178, 181, 121, 141, 91, 73, 7, 196, 253, 223, 250, 142, 237, 105, 12, 84, 33, 157, 65, 118, 154, 144, 164, 219, 234, 235, 2, 17, 0, 0, 0, 3, 22, 38, 19, 170, 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