Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c83763040b35abb2af30c8d88b1053ed586bc9a682840b6baa01192d2870eaad

Tx prefix hash: d70628813c6f845ef6f883f7fa386d963a624996a0af72ab0f61d2f9d00f74e8
Tx public key: 43079c796188f8221c0fbfb2bdbf45ee0fd458b816892ab4cb374ef50f3783bd
Timestamp: 1702477689 Timestamp [UCT]: 2023-12-13 14:28:09 Age [y:d:h:m:s]: 01:043:10:30:34
Block: 912303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292358 RingCT/type: yes/0
Extra: 0143079c796188f8221c0fbfb2bdbf45ee0fd458b816892ab4cb374ef50f3783bd02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 276c27afeaac8c0b8d42d9b2dba0f5ac3e844ada403462e98123fd57eb29ccec 0.600000000000 1369529 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": 912313, "vin": [ { "gen": { "height": 912303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "276c27afeaac8c0b8d42d9b2dba0f5ac3e844ada403462e98123fd57eb29ccec" } } ], "extra": [ 1, 67, 7, 156, 121, 97, 136, 248, 34, 28, 15, 191, 178, 189, 191, 69, 238, 15, 212, 88, 184, 22, 137, 42, 180, 203, 55, 78, 245, 15, 55, 131, 189, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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