Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 775c2162db42814b38173b2a08ac9f6598a9588ed6480c4812e774e892679a9a

Tx prefix hash: b67451ae829847cbea5da5a3c55ea8fe4c4bc35d1fdd2f16337b42ec6e1ee0f5
Tx public key: 0783e378cba5b2d69bde7516b9d34153294b906c655b258701826f9ff9cda737
Timestamp: 1732862783 Timestamp [UCT]: 2024-11-29 06:46:23 Age [y:d:h:m:s]: 00:356:17:05:50
Block: 1164100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252467 RingCT/type: yes/0
Extra: 010783e378cba5b2d69bde7516b9d34153294b906c655b258701826f9ff9cda7370211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ebe66de72834b2af24d1eee7371c1a2def9e3737bd968b9c3eedd073adad76d 0.600000000000 1649773 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": 1164110, "vin": [ { "gen": { "height": 1164100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ebe66de72834b2af24d1eee7371c1a2def9e3737bd968b9c3eedd073adad76d" } } ], "extra": [ 1, 7, 131, 227, 120, 203, 165, 178, 214, 155, 222, 117, 22, 185, 211, 65, 83, 41, 75, 144, 108, 101, 91, 37, 135, 1, 130, 111, 159, 249, 205, 167, 55, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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