Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18a60639c9c5f6704b3a731f80cdb1810e420e9df57834f815ce2f844bdc076

Tx prefix hash: 9a70041fbc571956dd6f3fa8b0d993deee183ace5ad0c490a7569e0bd4322d8a
Tx public key: 0818139c0aa6580bd7284ea41a8c8b2b65982cc2e54a5464e00d52fed65b5ab7
Timestamp: 1705714859 Timestamp [UCT]: 2024-01-20 01:40:59 Age [y:d:h:m:s]: 01:073:17:21:26
Block: 939094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313794 RingCT/type: yes/0
Extra: 010818139c0aa6580bd7284ea41a8c8b2b65982cc2e54a5464e00d52fed65b5ab70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d071c8ebc4cc19366fd2cac76711aa2030f039ac6ca1b7752b33f0107e1d40e 0.600000000000 1397178 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": 939104, "vin": [ { "gen": { "height": 939094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d071c8ebc4cc19366fd2cac76711aa2030f039ac6ca1b7752b33f0107e1d40e" } } ], "extra": [ 1, 8, 24, 19, 156, 10, 166, 88, 11, 215, 40, 78, 164, 26, 140, 139, 43, 101, 152, 44, 194, 229, 74, 84, 100, 224, 13, 82, 254, 214, 91, 90, 183, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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