Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283ee2aea3c8df88c94c44a586344468dc96fd9ea39613a3127802f9b38afc84

Tx prefix hash: 3dd4494834a7bd161f2fb9aaddc8f97c909887fd4a43f251947835e100923b45
Tx public key: cded0a136836d6763ed07b81e8e3272c6bc37c8865c872ed7c5e34fb82c555a4
Timestamp: 1734020786 Timestamp [UCT]: 2024-12-12 16:26:26 Age [y:d:h:m:s]: 00:027:11:13:43
Block: 1173706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19621 RingCT/type: yes/0
Extra: 01cded0a136836d6763ed07b81e8e3272c6bc37c8865c872ed7c5e34fb82c555a4021100000002a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd539a538caae2717d1a4f82c6d7c9b150aa08febc5edb134ec477ca3a175543 0.600000000000 1659757 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": 1173716, "vin": [ { "gen": { "height": 1173706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd539a538caae2717d1a4f82c6d7c9b150aa08febc5edb134ec477ca3a175543" } } ], "extra": [ 1, 205, 237, 10, 19, 104, 54, 214, 118, 62, 208, 123, 129, 232, 227, 39, 44, 107, 195, 124, 136, 101, 200, 114, 237, 124, 94, 52, 251, 130, 197, 85, 164, 2, 17, 0, 0, 0, 2, 162, 215, 95, 68, 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