Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f2dc4e410b925fe415331517330f27c5b4ce79016d5aa3dabc54b551f9917e

Tx prefix hash: 649d72c58f150b34c41aa42504d8b9046ce0295830d4874e53326f89a1fc9da6
Tx public key: c5755ea6f312d9b87adcee4aab0be87daac092eb9117fb9414db9278a1718d02
Timestamp: 1708475975 Timestamp [UCT]: 2024-02-21 00:39:35 Age [y:d:h:m:s]: 01:050:06:55:24
Block: 962010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296981 RingCT/type: yes/0
Extra: 01c5755ea6f312d9b87adcee4aab0be87daac092eb9117fb9414db9278a1718d0202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ea4e37d39d30fbb8d29afe8a79eb6ab94c8cdbcb575daedacb405a217c22db5 0.600000000000 1421633 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": 962020, "vin": [ { "gen": { "height": 962010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ea4e37d39d30fbb8d29afe8a79eb6ab94c8cdbcb575daedacb405a217c22db5" } } ], "extra": [ 1, 197, 117, 94, 166, 243, 18, 217, 184, 122, 220, 238, 74, 171, 11, 232, 125, 170, 192, 146, 235, 145, 23, 251, 148, 20, 219, 146, 120, 161, 113, 141, 2, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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