Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84fe93e23992907fcf5f21b8b0ebb808e65bfeca2647e0191d8701d16843114c

Tx prefix hash: 28856eab1eb9645ba5966bb157178d020935cbf7788c1f8fa193b3d442214601
Tx public key: 1c6c846c3d6ad00f4b6587fb6fb0b2afe466345df5cc959e18aafc48868e9f4f
Timestamp: 1632157084 Timestamp [UCT]: 2021-09-20 16:58:04 Age [y:d:h:m:s]: 03:103:10:36:07
Block: 337658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849946 RingCT/type: yes/0
Extra: 011c6c846c3d6ad00f4b6587fb6fb0b2afe466345df5cc959e18aafc48868e9f4f02110000002b36fe6557000000000000000000

1 output(s) for total of 46.687359593000 dcy

stealth address amount amount idx
00: 14566ea216a400d5fc1e91213def54e35c85fb534aa55212b84dfb10c79a3e9a 46.687359593000 695199 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": 337668, "vin": [ { "gen": { "height": 337658 } } ], "vout": [ { "amount": 46687359593, "target": { "key": "14566ea216a400d5fc1e91213def54e35c85fb534aa55212b84dfb10c79a3e9a" } } ], "extra": [ 1, 28, 108, 132, 108, 61, 106, 208, 15, 75, 101, 135, 251, 111, 176, 178, 175, 228, 102, 52, 93, 245, 204, 149, 158, 24, 170, 252, 72, 134, 142, 159, 79, 2, 17, 0, 0, 0, 43, 54, 254, 101, 87, 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