Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 804a7382031b149828b56be3f4d5530bc776e99207d807b1f4a52d9cfbf86a5c

Tx prefix hash: 4b7190579f63e26c45f0beccc25667f35a6de1bec630bad8c01b9eff382a36bd
Tx public key: 864314ebc48084ebb5397b6b3b701b6de5c3d7d04b6cd3adc0fa7aa60a57f882
Timestamp: 1703000334 Timestamp [UCT]: 2023-12-19 15:38:54 Age [y:d:h:m:s]: 01:333:00:58:16
Block: 916623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496872 RingCT/type: yes/0
Extra: 01864314ebc48084ebb5397b6b3b701b6de5c3d7d04b6cd3adc0fa7aa60a57f88202110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b7d5b45932b50ebd271b9ac1889e189d1b1695109207c436bfaf799018588f3 0.600000000000 1374181 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": 916633, "vin": [ { "gen": { "height": 916623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b7d5b45932b50ebd271b9ac1889e189d1b1695109207c436bfaf799018588f3" } } ], "extra": [ 1, 134, 67, 20, 235, 196, 128, 132, 235, 181, 57, 123, 107, 59, 112, 27, 109, 229, 195, 215, 208, 75, 108, 211, 173, 192, 250, 122, 166, 10, 87, 248, 130, 2, 17, 0, 0, 0, 11, 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