Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b614b138600b7ca83a75c006122232f60d7f80471b8edb58d06eb4f9431bab5

Tx prefix hash: ebcde572ef2a89c79756e22ee5660a2c76c39d041a26c6d58d4d31ccd20eb541
Tx public key: bf20e43346dbaaacd3ec363353e668a0b8b8d322098123c51d616af976b4203e
Timestamp: 1584921765 Timestamp [UCT]: 2020-03-23 00:02:45 Age [y:d:h:m:s]: 04:239:16:00:30
Block: 86845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068208 RingCT/type: yes/0
Extra: 01bf20e43346dbaaacd3ec363353e668a0b8b8d322098123c51d616af976b4203e0211000000174943cd9f000000000000000000

1 output(s) for total of 316.407845735000 dcy

stealth address amount amount idx
00: 9dc53472bfa05bed9e990460d08b482a84322c6fd7a9c0560b5c9dd7aa8ca733 316.407845735000 156671 of 0

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": 86855, "vin": [ { "gen": { "height": 86845 } } ], "vout": [ { "amount": 316407845735, "target": { "key": "9dc53472bfa05bed9e990460d08b482a84322c6fd7a9c0560b5c9dd7aa8ca733" } } ], "extra": [ 1, 191, 32, 228, 51, 70, 219, 170, 172, 211, 236, 54, 51, 83, 230, 104, 160, 184, 184, 211, 34, 9, 129, 35, 197, 29, 97, 106, 249, 118, 180, 32, 62, 2, 17, 0, 0, 0, 23, 73, 67, 205, 159, 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