Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43dd741315a3b4e4ce5a6938dc03283179faead25a4157e3953292ef07f85c82

Tx prefix hash: 5941e46811fc376a66b87fd003904c2a0908bd8e9a7438d23d6c6b288d931857
Tx public key: fd9ff46d10372b12b42b7a95f0ae2a2c5646e7b8cdccdbeb5eb280e803b748d0
Timestamp: 1577882546 Timestamp [UCT]: 2020-01-01 12:42:26 Age [y:d:h:m:s]: 05:109:05:21:23
Block: 36338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227971 RingCT/type: yes/0
Extra: 01fd9ff46d10372b12b42b7a95f0ae2a2c5646e7b8cdccdbeb5eb280e803b748d002110000003d4943cd9f000000000000000000

1 output(s) for total of 465.155300735000 dcy

stealth address amount amount idx
00: 731b7c59b0e89a0d864d32451734e090ba80a3de880ea266d034d35de5e593a1 465.155300735000 61533 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": 36348, "vin": [ { "gen": { "height": 36338 } } ], "vout": [ { "amount": 465155300735, "target": { "key": "731b7c59b0e89a0d864d32451734e090ba80a3de880ea266d034d35de5e593a1" } } ], "extra": [ 1, 253, 159, 244, 109, 16, 55, 43, 18, 180, 43, 122, 149, 240, 174, 42, 44, 86, 70, 231, 184, 205, 204, 219, 235, 94, 178, 128, 232, 3, 183, 72, 208, 2, 17, 0, 0, 0, 61, 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