Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c605d51f9569c9d30ff4d140821650ea7c645240c566d1f7d312dfcaafb60370

Tx prefix hash: 8e9405d59d07a8ccd87aefd440cd79ffc6b0bd404daabc00649c4e7bd4efcaf2
Tx public key: 70f5a6ac30cb03d8f1c6bc5aec50d79437819e2977eeb9ba5d1bfc9151875452
Timestamp: 1725457625 Timestamp [UCT]: 2024-09-04 13:47:05 Age [y:d:h:m:s]: 00:128:12:10:46
Block: 1102813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91890 RingCT/type: yes/0
Extra: 0170f5a6ac30cb03d8f1c6bc5aec50d79437819e2977eeb9ba5d1bfc9151875452021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ff68c80d8d1b36b92ba340340165ad759b44201ec609d965fc710224b6a7b60 0.600000000000 1579392 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": 1102823, "vin": [ { "gen": { "height": 1102813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ff68c80d8d1b36b92ba340340165ad759b44201ec609d965fc710224b6a7b60" } } ], "extra": [ 1, 112, 245, 166, 172, 48, 203, 3, 216, 241, 198, 188, 90, 236, 80, 215, 148, 55, 129, 158, 41, 119, 238, 185, 186, 93, 27, 252, 145, 81, 135, 84, 82, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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