Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 622a9bd839fb9fc0f1784d17b374015aeac80a4c69eb2e923adec2885a1b9e75

Tx prefix hash: ae8f765a7efba311f60030a6f1e8f9e0592e14dc5aa94324f2308b14192b019a
Tx public key: 80d19f0903dc26cd054e8ceab86f793bdc5a28c14247df2fa575b0a2f0159cf5
Timestamp: 1722782950 Timestamp [UCT]: 2024-08-04 14:49:10 Age [y:d:h:m:s]: 01:098:05:40:08
Block: 1080620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328696 RingCT/type: yes/0
Extra: 0180d19f0903dc26cd054e8ceab86f793bdc5a28c14247df2fa575b0a2f0159cf502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb318c267422f51e44be701edb8065e2cb908a5a760b1eb012367b5aa219032 0.600000000000 1554055 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": 1080630, "vin": [ { "gen": { "height": 1080620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb318c267422f51e44be701edb8065e2cb908a5a760b1eb012367b5aa219032" } } ], "extra": [ 1, 128, 209, 159, 9, 3, 220, 38, 205, 5, 78, 140, 234, 184, 111, 121, 59, 220, 90, 40, 193, 66, 71, 223, 47, 165, 117, 176, 162, 240, 21, 156, 245, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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