Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb63c3644f830aa95d1f163b862b66511210de1e02ff4263ad337e04795bcbc1

Tx prefix hash: 89a9ccae4065a88bdadb3e3aaea91f7681a4e2dd3b9f0bf4201a7a8fc3930230
Tx public key: b517998e0a0197abe98dd09fd675e5c3a6985f86c314489c8a3e8a3f792387c1
Timestamp: 1577499582 Timestamp [UCT]: 2019-12-28 02:19:42 Age [y:d:h:m:s]: 04:364:06:06:06
Block: 33165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149592 RingCT/type: yes/0
Extra: 01b517998e0a0197abe98dd09fd675e5c3a6985f86c314489c8a3e8a3f792387c102110000000a4943cd9f000000000000000000

1 output(s) for total of 476.561500430000 dcy

stealth address amount amount idx
00: d777801bd84ad1b97639ee5065eedd1d2ff8f33af740165305b7010e9e54883d 476.561500430000 55442 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": 33175, "vin": [ { "gen": { "height": 33165 } } ], "vout": [ { "amount": 476561500430, "target": { "key": "d777801bd84ad1b97639ee5065eedd1d2ff8f33af740165305b7010e9e54883d" } } ], "extra": [ 1, 181, 23, 153, 142, 10, 1, 151, 171, 233, 141, 208, 159, 214, 117, 229, 195, 166, 152, 95, 134, 195, 20, 72, 156, 138, 62, 138, 63, 121, 35, 135, 193, 2, 17, 0, 0, 0, 10, 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