Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a989cd8f102e961f64c7fca4d5924b345d243801d7877b40dff0c71a826d23f5

Tx prefix hash: 503fa11b350fd2b7b0a6f785f6eb366f8512d8ea6797480a062753260122a87f
Tx public key: 0e836b2654dc9212c0e3887ab58f9dc7170780168a80c04ba60a4a8333ad3dc7
Timestamp: 1707956351 Timestamp [UCT]: 2024-02-15 00:19:11 Age [y:d:h:m:s]: 01:028:23:01:58
Block: 957701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281743 RingCT/type: yes/0
Extra: 010e836b2654dc9212c0e3887ab58f9dc7170780168a80c04ba60a4a8333ad3dc70211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9cc5e4125daade7d37c12b04a6a38f4d015626b236904fadb35f541d347b0a8 0.600000000000 1417048 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": 957711, "vin": [ { "gen": { "height": 957701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9cc5e4125daade7d37c12b04a6a38f4d015626b236904fadb35f541d347b0a8" } } ], "extra": [ 1, 14, 131, 107, 38, 84, 220, 146, 18, 192, 227, 136, 122, 181, 143, 157, 199, 23, 7, 128, 22, 138, 128, 192, 75, 166, 10, 74, 131, 51, 173, 61, 199, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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