Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dce3348165379eff51a65d252ca8236f54d8173d40e601fe2245f34ae3ecc09f

Tx prefix hash: 5207ec9f9182c9f8f079b26e3db09ffc5f0bfae2813eb21c01b5c4fad9b89dbe
Tx public key: f93f31f4c00ed620d0e1dafcabf5506389b4bd42b80ec4ee6ae28fe6aab4336b
Timestamp: 1710651439 Timestamp [UCT]: 2024-03-17 04:57:19 Age [y:d:h:m:s]: 01:086:00:30:58
Block: 980073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322471 RingCT/type: yes/0
Extra: 01f93f31f4c00ed620d0e1dafcabf5506389b4bd42b80ec4ee6ae28fe6aab4336b02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94ecdee869a9fe3966351e1fe3830840ed34a7028074010368d584d57d8e8db0 0.600000000000 1440132 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": 980083, "vin": [ { "gen": { "height": 980073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94ecdee869a9fe3966351e1fe3830840ed34a7028074010368d584d57d8e8db0" } } ], "extra": [ 1, 249, 63, 49, 244, 192, 14, 214, 32, 208, 225, 218, 252, 171, 245, 80, 99, 137, 180, 189, 66, 184, 14, 196, 238, 106, 226, 143, 230, 170, 180, 51, 107, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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