Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3ef04a799d12b1d2bf7dddf803fa9c8c3fd43aa79339a5f7076cc375f1882d2

Tx prefix hash: 8b9693691a128d6ac0d5b24d0a81a84350af1c700a381f5e8910b12832558b58
Tx public key: 7f35b43790e9de8e863f9e93df03726a7ecf755a57d72adc4566b671d31d0330
Timestamp: 1648658031 Timestamp [UCT]: 2022-03-30 16:33:51 Age [y:d:h:m:s]: 03:215:18:02:08
Block: 469687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 932191 RingCT/type: yes/0
Extra: 017f35b43790e9de8e863f9e93df03726a7ecf755a57d72adc4566b671d31d03300211000000242e6b1fd5000000000000000000

1 output(s) for total of 17.050708550000 dcy

stealth address amount amount idx
00: 0afc98f4633bcbcb85695103a4b982515623aba8da18596e0e987ed95290259d 17.050708550000 888679 of 0

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": 469697, "vin": [ { "gen": { "height": 469687 } } ], "vout": [ { "amount": 17050708550, "target": { "key": "0afc98f4633bcbcb85695103a4b982515623aba8da18596e0e987ed95290259d" } } ], "extra": [ 1, 127, 53, 180, 55, 144, 233, 222, 142, 134, 63, 158, 147, 223, 3, 114, 106, 126, 207, 117, 90, 87, 215, 42, 220, 69, 102, 182, 113, 211, 29, 3, 48, 2, 17, 0, 0, 0, 36, 46, 107, 31, 213, 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